Introducing different packages to handle cross-chain functionalities, that can be used to build and support a cross-chain adapter in any dapp.
Each package can be used as a standalone component, and the dapp should decide what packages it needs following its business logic.

Live example https://aptos-labs.github.io/aptos-wallet-adapter/nextjs-example-testing/swap

wallet-adapter-aggregator:
A folder that contains multiple packages, each represents a Wallet. In addition, it holds a wallet-adapter-aggregator-core package that holds the abstract class that each wallet must implement.
I implemented a conversion layer for each cross-chain wallet, to represent it as the official Aptos wallet standard. There are some issues I have seen, and I am open for any suggestions.

• The Aptos wallet standard defines input and output types, and expects each feature to follow it. That becomes a bit difficult when trying to convert each wallet function/feature.
• Overall, for Solana and I believe other future chains we can handle the types, but when it comes to EVM it is more complex. For example, returning AccountInfo from the connect() or getAccount() methods, is almost impossible because 1) this class represents an Aptos account (and therefore a 32 byte account) and 2) there is no way to retrieve the connected account publicKey from the account address (unless you submitted a transaction)

I am open for any implementation suggestions.

cross-chain-core:
A package that holds a cross-chain logic. Currently only provides CCTP transfer logic with Wormhole as the provider. In the Future, we will support more providers (LayerZero, Cellar, etc) and add it to that package.
In addition, this package can expose some related APIs like getAccountUsdcBalance() (still debating whether this should live in this package, or be part of the wallet features).

The CrossChainCore class accepts different dapp properties

• network: Network; // the network to use
• disableTelemetry?: boolean;

And the startCCTPTransfer() method in the WormholeProvider class accepts

• sourceChain: Chain;
• wallet: AdapterWallet;
• destinationAddress: AccountAddressInput;
• mainSigner: Account;
• sponsorAccount?: Account | Partial<Record<Network, string>>; // a generated account or gas station key

cross-chain-react
A React state provider that uses

• The cross-chain-core package
• The wallet aggregator package the dapp wants to support

Next steps:

• Gas station support
• Implement signInWithX
• Aptos aggregator wallet
• Solana priority fee user config // currently sets priority fee by default, it should come from the dapp config
• RPC user config
• Expose getUsdcBalance() API
• DAA support (blocked by [WIP] adding common doman AA aptos-core#16006, already ready to go here [Draft] Implement domain abstracted account aptos-ts-sdk#648)